Cell management method, trigger condition configuration method, terminal device, and network-side device

ABSTRACT

A cell management method, a trigger condition configuration method, a terminal device, and a network-side device are provided. The method includes: receiving configuration information of a trigger condition and configuration information of a trigger event that are sent by a network-side device, where an association relationship exists between the configuration information of the trigger condition and the configuration information of the trigger event, and configuration information of one trigger condition is associated with configuration information of at least two trigger events; determining, based on the configuration information of the at least two trigger events associated with the configuration information of the trigger condition, whether the trigger condition is satisfied; and when the trigger condition is satisfied, initiating a radio resource control RRC procedure for cell management.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is continuation-in-part of U.S. patent application Ser.No. 17/112,627 filed on Dec. 4, 2020 which is continuation applicationof PCT International Application No. PCT/CN2019/088121 filed on May 23,2019, which claims priority to Chinese Patent Application No.201810565750.1, filed in China on Jun. 4, 2018, the disclosures of whichare incorporated in their entireties by reference herein.

TECHNICAL FIELD

This disclosure relates to the field of communications technologies, andin particular, to a cell management method, a trigger conditionconfiguration method, a terminal device, and a network-side device.

BACKGROUND

In a wireless communications system, during communication between userequipment (UE) and a network-side device, the UE in a connected statemay move from a coverage area of one base station (a base station towhich the UE is currently connected) to a coverage area of another basestation due to mobility. In this case, the UE needs to switch from anoriginal radio channel to a new radio channel, that is, completehandover.

A conditional handover mode is being researched for the 5th generation(5G) mobile communications technology to increase a handoverprobability. Conditional handover means that a base station prepares oneor more candidate target cells for the UE beforehand based on ameasurement result reported by the UE, and sends a conditional handovercommand to the UE, where the conditional handover command includes alist of candidate target cells, handover trigger conditionscorresponding to the candidate target cells, resource configurationscorresponding to the candidate target cells, and the like; and the UEdoes not perform cell handover immediately after receiving theconditional handover command, but performs cell handover only afterdetermining that a candidate cell satisfies a preset handover triggercondition. Likewise, such conditional cell change mode may also beapplied to a procedure such as addition or change or release ormodification of a secondary node (SN) that is triggered by mobility ofthe UE in a dual connectivity (DC) architecture, to further improveflexibility of management of a secondary cell group.

In a condition-triggered cell management (for example, cell handover orcell addition or cell deletion) procedure, a network side needs toconfigure a trigger condition for the UE, so that the UE autonomouslyinitiates the cell management procedure. However, no related solution isavailable for configuring a trigger condition in the communicationssystem in the related art.

SUMMARY

Embodiments of this disclosure provide a cell management method, atrigger condition configuration method, a terminal device, and anetwork-side device to standardize how a trigger condition is configuredfor a condition-triggered cell management procedure.

According to a first aspect, an embodiment of this disclosure provides acell management method. The method includes:

-   -   receiving configuration information of a trigger condition and        configuration information of a trigger event that are sent by a        network-side device, where an association relationship exists        between the configuration information of the trigger condition        and the configuration information of the trigger event, and        configuration information of one trigger condition is associated        with configuration information of at least two trigger events;    -   determining, based on the configuration information of the at        least two trigger events associated with the configuration        information of the trigger condition, whether the trigger        condition is satisfied; and    -   when the trigger condition is satisfied, initiating a radio        resource control RRC procedure for cell management.

According to a second aspect, an embodiment of this disclosure furtherprovides a trigger condition configuration method. The method includes:

-   -   obtaining configuration information of a trigger condition and        configuration information of a trigger event; and    -   sending the configuration information of the trigger condition        and the configuration information of the trigger event to a        terminal device, where an association relationship exists        between the configuration information of the trigger condition        and the configuration information of the trigger event, and        configuration information of one trigger condition is associated        with configuration information of at least two trigger events.

According to a third aspect, an embodiment of this disclosure furtherprovides a terminal device. The terminal device includes:

-   -   a receiving module, configured to receive configuration        information of a trigger condition and configuration information        of a trigger event that are sent by a network-side device, where        an association relationship exists between the configuration        information of the trigger condition and the configuration        information of the trigger event, and configuration information        of one trigger condition is associated with configuration        information of at least two trigger events;    -   a determining module, configured to determine, based on the        configuration information of the at least two trigger events        associated with the configuration information of the trigger        condition, whether the trigger condition is satisfied; and    -   an initiation module, configured to initiate a radio resource        control RRC procedure for cell management when the trigger        condition is satisfied.

According to a fourth aspect, an embodiment of this disclosure furtherprovides a network-side device. The network-side device includes:

-   -   an obtaining module, configured to obtain configuration        information of a trigger condition and configuration information        of a trigger event; and    -   a sending module, configured to send the configuration        information of the trigger condition and the configuration        information of the trigger event to a terminal device, where an        association relationship exists between the configuration        information of the trigger condition and the configuration        information of the trigger event, and configuration information        of one trigger condition is associated with configuration        information of at least two trigger events.

According to a fifth aspect, an embodiment of this disclosure furtherprovides a terminal device, including a processor, a memory, and acomputer program stored in the memory and capable of running on theprocessor, where when the computer program is executed by the processor,steps of the cell management method according to the first aspect areimplemented.

According to a sixth aspect, an embodiment of this disclosure furtherprovides a network-side device, including a processor, a memory, and acomputer program stored in the memory and capable of running on theprocessor, where when the computer program is executed by the processor,steps of the trigger condition configuration method according to thesecond aspect are implemented.

According to a seventh aspect, an embodiment of this disclosure furtherprovides a computer-readable storage medium, where the computer-readablestorage medium stores a computer program, and when the computer programis executed by a processor, steps of the cell management methodaccording to the first aspect are implemented, or steps of the triggercondition configuration method according to the second aspect areimplemented.

In the embodiments of this disclosure, configuration information of atrigger condition and configuration information of a trigger event thatare sent by a network-side device are received, where an associationrelationship exists between the configuration information of the triggercondition and the configuration information of the trigger event, andconfiguration information of one trigger condition is associated withconfiguration information of at least two trigger events; whether thetrigger condition is satisfied is determined based on the configurationinformation of the at least two trigger events associated with theconfiguration information of the trigger condition; and when the triggercondition is satisfied, a radio resource control RRC procedure for cellmanagement is initiated. This standardizes how a trigger condition isconfigured for a condition-triggered cell management procedure.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of thisdisclosure more clearly, the following briefly describes theaccompanying drawings required for describing the embodiments of thisdisclosure. Apparently, the accompanying drawings in the followingdescription show merely some embodiments of this disclosure, and aperson of ordinary skill in the art may still derive other drawings fromthese accompanying drawings without creative efforts.

FIG. 1 is a flowchart of a conditional handover procedure according toan embodiment of this disclosure;

FIG. 2 is a structural diagram of a network system to which anembodiment of this disclosure may be applied;

FIG. 3 is a flowchart of a cell management method according to anembodiment of this disclosure;

FIG. 4 is a flowchart of a trigger condition configuration methodaccording to an embodiment of this disclosure;

FIG. 5 is a flowchart of a cell management method according to anotherembodiment of this disclosure;

FIG. 6 is a structural diagram of a terminal device according to anembodiment of this disclosure;

FIG. 7 is a structural diagram of a network-side device according to anembodiment of this disclosure;

FIG. 8 is a structural diagram of a terminal device according to anotherembodiment of this disclosure; and

FIG. 9 is a structural diagram of a network-side device according toanother embodiment of this disclosure.

DESCRIPTION OF EMBODIMENTS

The following clearly describes the technical solutions in theembodiments with reference to the accompanying drawings in theembodiments. Apparently, the described embodiments are merely somerather than all of the embodiments of this disclosure. All otherembodiments that a person of ordinary skill in the art obtains withoutcreative efforts based on the embodiments of this disclosure shall fallwithin the protection scope of this disclosure.

The terms “first”, “second”, and the like in this specification andclaims of this application are used to distinguish between similarobjects instead of describing a specific order or sequence. It should beunderstood that numbers used in this way is interchangeable inappropriate circumstances so that the embodiments of this applicationdescribed herein can be implemented in other orders than the orderillustrated or described herein. In addition, the terms “include”,“have”, and any other variant thereof are intended to cover anon-exclusive inclusion. For example, a process, method, system,product, or device that includes a list of steps or units is notnecessarily limited to those steps or units that are expressly listed,but may include other steps or units that are not expressly listed orare inherent to such process, method, system, product, or device. Inaddition, the term “and/or” used in this specification and claimsindicates at least one of the connected objects. For example, “A and/orB and/or C” represents the following seven cases: only A, only B, onlyC, both A and B, both B and C, both A and C, and all A, B, and C.

For ease of understanding, the following describes some terms used inthe embodiments of this disclosure.

Conditional Handover:

In the embodiments, a conditional handover procedure may include thefollowing steps.

Step a: A source node sends a handover request (HO Request) to one ormore target nodes.

For example, in FIG. 1 , a source node sends a handover request to atarget node a and a target node b.

Step b: The target node feeds back handover acknowledgement information,that is, a handover request response (HO Request ACK), to the sourcenode.

As shown in FIG. 1 , the target node a and the target node b send ahandover request response to the source node respectively.

Step c: The source node sends configuration information of conditionalhandover to a terminal.

Step d: The terminal evaluates conditions of candidate cells, andselects a target cell for handover.

In this step, the terminal evaluates whether the conditions of thecandidate cells are satisfied, and may select a target cell thatsatisfies a condition for handover.

As shown in FIG. 1 , the terminal may evaluate whether conditions of thetarget node a and the target node b are satisfied, and when the terminaldetermines that the condition of the target node a is satisfied, theterminal may initiate a random access procedure to the target node a.

Step e: The terminal initiates a random access procedure in the selectedtarget cell.

As shown in FIG. 1 , the terminal selects the target node a to initiaterandom access.

Step f: The terminal sends handover complete information to the selectedtarget node.

As shown in FIG. 1 , the terminal sends handover complete information(that is, HO Complete) to the target node a.

Step g: The source node sends a conditional handover cancellationcommand to another unselected target node.

As shown in FIG. 1 , the source node sends a conditional handovercancellation command (that is, Conditional HO Cancellation) to thetarget node b.

Step h: The another unselected target node sends a conditional handovercancellation confirmation command to the source node.

As shown in FIG. 1 , the target node b sends a conditional handovercancellation command (that is, Conditional HO Cancellation Confirmation)to the source node.

Dual Connectivity:

In a 5th generation (5G) communications system, a dual connectivity (DC)architecture is introduced. The DC architecture may include two cellgroups, which are a master cell group (MCG) and a secondary cell group(SCG) respectively. The MCG corresponds to a master node (MN) on anetwork side, and the SCG corresponds to a secondary node SN) on thenetwork side. In addition, the MCG may include a primary cell (PCell)and one or more secondary cells (SCell), and the secondary cell groupmay include a primary secondary cell (PSCell) and one or more SCells.

FIG. 2 is a structural diagram of a network system to which anembodiment of this disclosure may be applied. As shown in FIG. 2 , thenetwork system includes a terminal device 11, a source node 12, and atarget node 13. The terminal device 11 may also be referred to as userequipment (UE). The terminal device 11 may be a terminal-side devicesuch as a mobile phone, a tablet computer (Tablet Personal Computer), alaptop computer, a personal digital assistant (PDA), a mobile Internetdevice (MID), a wearable device, or a vehicle-mounted device. It shouldbe noted that a specific type of the terminal device 11 is not limitedin this embodiment of this disclosure. The source node 12 may be one ofnetwork nodes to which the terminal device 11 is currently connected.For example, if the network nodes to which the terminal device 11 iscurrently connected include an MN and an SN, the source node 12 may beone of the MN and the SN. The target node 13 may be one of the networknodes to which the terminal device 11 is currently connected, or may bea network node to which the terminal device 11 is currently notconnected. Because cell management performed by the terminal device 11may include but is not limited to at least one of cell handover, celladdition, cell deletion, and cell change in this embodiment of thisdisclosure, the terminal device 11 may delete a connection between theterminal device 11 and the target node 13 or establish a connection tothe target node 13 in a process of performing cell management. Thenetwork structure to which the embodiments of this disclosure areapplied may include one or more target nodes 13, and one target node 13is used as an example in the figure.

In addition, in this embodiment of this disclosure, the network node maybe a base station in 5G or a later version (for example, a 5G NR NB), ora base station in another communications system, or may be referred toas a NodeB, an evolved NodeB, or an MN, or an SN, or other terms in thisfield. As long as a same technical effect is achieved, the base stationis not limited to a specific technical term.

In addition, this embodiment of this disclosure may be applied to aconditional handover procedure, that is, the source node 12 and thetarget node 13 may be a source base station and a target base station inthe conditional handover procedure; or this embodiment of thisdisclosure may be applied to a DC architecture, that is, the source node12 and the target node 13 may be a source SN and a target SN in the DCarchitecture, or a source MN and a target SN in the DC architecture.

It should be noted that specific functions of the terminal device 11,the source node 12, and the target node 13 in this embodiment of thisdisclosure are described in detail by using the following embodiments.

An embodiment of this disclosure provides a cell management method,applied to a terminal device. FIG. 3 is a flowchart of a cell managementmethod according to an embodiment of this disclosure. As shown in FIG. 3, the method includes the following steps.

Step 301: Receive configuration information of a trigger condition andconfiguration information of a trigger event that are sent by anetwork-side device, where an association relationship exists betweenthe configuration information of the trigger condition and theconfiguration information of the trigger event, and configurationinformation of one trigger condition is associated with configurationinformation of at least two trigger events.

In this implementation, the network-side device may send theconfiguration information of the trigger condition and the configurationinformation of the trigger event by using a radio resource control (RRC)message. Certainly, the message is not limited in this embodiment ofthis disclosure. For example, the message may also be another downlinkmessage.

It may be understood that the network-side device may send theconfiguration information of the trigger condition and the configurationinformation of the trigger event to the terminal device separately byusing different RRC messages, or may send the configuration informationof the trigger condition and the configuration information of thetrigger event to the terminal device by using a same RRC message.

The configuration information of the trigger condition may includeconfiguration information of one or more trigger conditions, andconfiguration information of each trigger condition is associated withconfiguration information of at least two trigger events.

The configuration information of the trigger condition may include butis not limited to effective duration of the trigger condition. Theconfiguration information of the trigger event may include but is notlimited to at least one of a type of the trigger event (for example, atrigger event based on a measurement result of a target cell, a triggerevent based on a measurement result of a serving cell, or a triggerevent based on a packet loss rate in data transmission of a servingcell), a measurement parameter of the trigger event (such as referencesignal received power (RSRP), reference signal received quality (RSRQ),a signal to interference plus noise ratio (SINR), or a latency), and athreshold of the trigger event.

Optionally, the receiving configuration information of a triggercondition and configuration information of a trigger event that are sentby a network-side device may include:

-   -   receiving the configuration information of the trigger condition        and the configuration information of the trigger event that are        sent by a source node; or    -   receiving the configuration information of the trigger condition        and the configuration information of the trigger event that are        sent by a target node through a source node.

In an implementation, the configuration information of the triggercondition and the configuration information of the trigger event may besent to the terminal device through the source node. Before the sourcenode sends the configuration information of the trigger condition andthe configuration information of the trigger event, the source node maydetermine the configuration information of the trigger condition and theconfiguration information of the trigger event through negotiationbetween the source node and one or more target nodes. The negotiationherein may be that the source node and the target node perform signalinginteraction to determine the configuration information of the triggercondition and the configuration information of the trigger event.

For example, after receiving configuration information of a target cellof one or more target nodes, the source node associates theconfiguration information of the trigger condition with theconfiguration information of the trigger event, and may send theassociated configuration information of the trigger condition andconfiguration information of the trigger event by using an RRC message.It should be noted that one target node may correspond to configurationinformation of one or more target cells.

Optionally, in some implementations, a conditional handover (CHO) isdefined as a handover that is executed by a UE when one or more handoverexecution conditions are met. The UE starts evaluating the executioncondition(s) upon receiving CHO configuration, and stops evaluating theexecution condition(s) once a handover is executed (legacy handover orconditional handover execution).

The following principle applies to CHO:

The CHO configuration contains configuration of CHO candidate cell(s)generated by candidate gNB(s) and execution condition(s) generated by asource gNB.

In this implementation, the configuration information of the triggercondition and the configuration information of the trigger event thatare sent by the source node are received. Therefore, the terminal devicecan receive, through the source node, the configuration information ofthe trigger condition and the configuration information of the triggerevent that correspond to one or more target nodes, and transmissionoverheads can be reduced.

In another implementation, the configuration information of the triggercondition and the configuration information of the trigger event thatare sent by the target node to the terminal device through the sourcenode may be received. Before the target node sends the configurationinformation of the trigger condition and the configuration informationof the trigger event, the target node may determine the configurationinformation of the trigger condition and the configuration informationof the trigger event through negotiation between the target node and thesource node.

For example, after receiving one or more pieces of request informationthat are sent by the source node for condition-triggered cellmanagement, the target node may associate the configuration informationof the trigger condition with the configuration information of thetrigger event, and send the associated configuration information of thetrigger condition and configuration information of the trigger event tothe source node, and the source node sends the configuration informationof the trigger condition and the configuration information of thetrigger event to the terminal device.

In this implementation, the configuration information of the triggercondition and the configuration information of the trigger event thatare sent by the target node through the source node are received.Therefore, the configuration information of the trigger condition andthe configuration information of the trigger event can be delivered bythe target node. The configuration information of the trigger conditionand the configuration information of the trigger event may betransparent to the source node, and merely need to be forwarded ortransmitted transparently. Therefore, complexity of the source node canbe reduced, and power consumption of the source node can be reduced.

It should be noted that the source node and the target node may be asource base station and a target base station respectively in a cellhandover procedure, or a source SN and a target SN in DC, or a source MNand a target SN in DC, or the like.

This is not limited in this embodiment of this disclosure.

Step 302: Determine, based on the configuration information of the atleast two trigger events associated with the configuration informationof the trigger condition, whether the trigger condition is satisfied.

In this implementation, because an association relationship existsbetween the configuration information of the trigger condition and theconfiguration information of the trigger event, and configurationinformation of one trigger condition is associated with configurationinformation of at least two trigger events, the terminal device mayevaluate, based on a network-side configuration, the configurationinformation of the at least two trigger events associated with theconfiguration information of the trigger condition, to determine whetherthe trigger condition is satisfied.

For example, when configuration information of any trigger event in theconfiguration information of the at least two trigger events associatedwith the configuration information of the trigger condition issatisfied, the terminal device determines that the trigger condition issatisfied; or when configuration information of all trigger events inthe configuration information of the at least two trigger eventsassociated with the configuration information of the trigger conditionis satisfied, the terminal device determines that the trigger conditionis satisfied.

For example, configuration information of at least two trigger eventsassociated with configuration information of a trigger condition Pincludes configuration information a of a trigger event andconfiguration information b of a trigger event, where a type of thetrigger event in the configuration information a of the trigger event isthat a measurement result of a target cell is greater than or equal to athreshold a and a measurement parameter of the trigger event is RSRP;and a type of the trigger event in the configuration information b ofthe trigger event is that a measurement result of a serving cell is lessthan or equal to a threshold b and a measurement parameter of thetrigger event is RSRP. In this case, when either of the configurationinformation a of the trigger event and the configuration information bof the trigger event is satisfied, the terminal device may determinethat the trigger condition P is satisfied, or when the configurationinformation a of the trigger event and the configuration information bof the trigger event are both satisfied, the terminal device maydetermine that the trigger condition P is satisfied.

For example, the configuration information of the trigger event may bestored in a trigger event information list, each entry in the triggerevent information list includes configuration information of a triggerevent and identification information corresponding to the configurationinformation of the trigger event. The identification information in thetrigger event information list may be measurement identification(MeasID), and if event(s) associated to all measId(s) within conditionaltrigger configuration (condTriggerConfig) for a target candidate cellwithin the stored cell configuration (condRRCReconfig) are fulfilled,then the target candidate cell within the stored condRRCReconfig,associated to that conditional reconfiguration identification(condReconfigId), is considered as a triggered cell, or, the conditionalreconfiguration execution is initiated.

Step 303: When the trigger condition is satisfied, initiate a radioresource control RRC procedure for cell management.

In this implementation, the cell management may include cell handover inconditional handover, or SN addition, change, release, or modificationtriggered by an MN in a DC architecture, or SN addition, change,release, or modification triggered by an SN in a DC architecture, or thelike.

In this embodiment of this disclosure, when the trigger condition issatisfied, the radio resource control (RRC) procedure is initiated tofurther perform a cell management procedure.

In the cell management method in this embodiment of this disclosure,configuration information of a trigger condition and configurationinformation of a trigger event that are sent by a network-side deviceare received, where an association relationship exists between theconfiguration information of the trigger condition and the configurationinformation of the trigger event, and configuration information of onetrigger condition is associated with configuration information of atleast two trigger events; whether the trigger condition is satisfied isdetermined based on the configuration information of the at least twotrigger events associated with the configuration information of thetrigger condition; and when the trigger condition is satisfied, a radioresource control RRC procedure for cell management is initiated. Thisstandardizes how a trigger condition is configured for acondition-triggered cell management procedure. In addition, the triggercondition is evaluated based on the configuration information of the atleast two trigger events associated with the configuration informationof the trigger condition, so that a decision result can be moreaccurate.

Optionally, the configuration information of the trigger condition isstored in a trigger condition information list, the configurationinformation of the trigger event is stored in a trigger eventinformation list, and the association relationship is stored in anassociation relationship list; or

the configuration information of the trigger condition and theconfiguration information of the trigger event are stored in a triggercondition configuration information list, where each entry in thetrigger condition configuration information list includes configurationinformation of a trigger condition and configuration information of atleast two trigger events corresponding to the configuration informationof the trigger condition.

In some implementations, the trigger condition configuration informationlist may be CondReconfigToAddModList, the configuration information ofthe trigger event may be condExecutionCond, each entry in the triggercondition configuration information list may be equivalent toCondReconfigToAddMod, and each entry in the trigger conditionconfiguration information list may include configuration information ofa trigger condition and configuration information of at least twotrigger events corresponding to the configuration information of thetrigger condition. The configuration information of the triggercondition may be equivalent to condReconfigId, and association with thecorresponding configuration information of at least two trigger eventsmay be implemented via condExecutionCond.

In an implementation, the configuration information of the triggercondition, the configuration information of the trigger event, and theassociation relationship between the configuration information of thetrigger condition and the configuration information of the trigger eventare separately stored in different lists. Each entry in the triggercondition information list may include configuration information of onetrigger condition, each entry in the trigger event information list mayinclude configuration information of one trigger event, and each entryin the association relationship list may include one associationrelationship.

It may be understood that because configuration information of onetrigger condition is associated with configuration information of atleast two trigger events in this embodiment of this disclosure, anassociation relationship includes an association relationship betweenconfiguration information of one trigger condition and configurationinformation of at least two trigger events. To be specific, each entryin the association relationship list includes an associationrelationship between configuration information of one trigger conditionand configuration information of at least two trigger events.

Optionally, each entry in the trigger condition information list mayinclude configuration information of a trigger condition andidentification information corresponding to the configurationinformation of the trigger condition; and

each entry in the trigger event information list may includeconfiguration information of a trigger event and identificationinformation corresponding to the configuration information of thetrigger event.

In this implementation, each entry in the trigger condition informationlist may include identification information in addition to configurationinformation of a trigger condition. For example, each entry in thetrigger condition information list includes configuration information ofa trigger condition and identification information (such as a conditionID) corresponding to the configuration information of the triggercondition. Therefore, the configuration information of the triggercondition may be identified by using the identification informationcorresponding to the configuration information of the trigger condition,or the configuration information of the trigger condition and theconfiguration information of the trigger event are associated by usingthe identification information.

Likewise, each entry in the trigger event information list may includeidentification information in addition to configuration information of atrigger event. For example, each entry in the trigger event informationlist includes configuration information of a trigger event andidentification information (such as an event ID) corresponding to theconfiguration information of the trigger event. Therefore, theconfiguration information of the trigger event may be identified byusing the identification information corresponding to the configurationinformation of the trigger event, or the configuration information ofthe trigger event and the configuration information of the triggercondition are associated by using the identification information.

Optionally, the association relationship may include:

-   -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and an entry tag of the trigger event information        list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information        corresponding to configuration information of a trigger event;        or    -   an association relationship between an entry tag of the trigger        condition information list and an entry tag of the trigger event        information list; or    -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and identification information in the trigger event        information list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information in the        trigger event information list.

In some implementations, the association relationship between theidentification information corresponding to the configurationinformation of the trigger condition and the identification informationin the trigger event information list may include:

an association relationship between the identification informationcorresponding to the configuration information of the trigger conditionand identification information corresponding to configurationinformation of a trigger event.

The identification information in the trigger event information list maybe measurement identification (MeaslD), or target terminalidentification, or event identification, etc.

In this implementation, an entry tag may be an entry in a list. Forexample, a first entry in the list is a tag 1, and a second entry in thelist is a tag 2.

It may be understood that, since configuration information of onetrigger condition is associated with configuration information of atleast two trigger events in the embodiments of this disclosure, anassociation relationship between identification informationcorresponding to configuration information of a trigger condition andidentification information corresponding to configuration information ofa trigger event includes at least: an association relationship betweenidentification information corresponding to configuration information ofone trigger condition and identification information corresponding toconfiguration information of at least two trigger events.

It may be understood that because configuration information of onetrigger condition is associated with configuration information of atleast two trigger events in this embodiment of this disclosure, anassociation relationship between identification informationcorresponding to configuration information of a trigger condition and anentry tag of the trigger event information list includes at least anassociation relationship between identification informationcorresponding to configuration information of one trigger condition andat least two entry tags of the trigger event information list; anassociation relationship between an entry tag of the trigger conditioninformation list and identification information corresponding toconfiguration information of a trigger event includes at least anassociation relationship between one entry tag of the trigger conditioninformation list and identification information corresponding toconfiguration information of at least two trigger events; and anassociation relationship between an entry tag of the trigger conditioninformation list and an entry tag of the trigger event information listincludes at least an association relationship between one entry tag ofthe trigger condition information list and at least two entry tags ofthe trigger event information list.

By using a plurality of association relationships provided in thisembodiment of this disclosure, configuration information of a triggercondition may be flexibly associated with configuration information of atrigger event, so that flexibility is improved.

In another implementation, the configuration information of the triggercondition and the configuration information of the trigger event may becorrespondingly stored in a same list. Each entry in the triggercondition configuration information list includes configurationinformation of a trigger condition and configuration information of atleast two trigger events corresponding to the configuration informationof the trigger condition. Therefore, configuration information of atrigger condition can be associated with configuration information of atrigger event by using one list, a more flexible configuration of anassociation between configuration information of a trigger condition andconfiguration information of a trigger event can be implemented, andsignaling transmission overheads can be reduced.

Optionally, the configuration information of the trigger event includesat least one of the following: the type of the trigger event, themeasurement parameter of the trigger event, the threshold of the triggerevent, a trigger type, and trigger duration.

In this implementation, the type of the trigger event, the measurementparameter of the trigger event, the threshold of the trigger event, thetrigger type, the trigger duration, and the like may be all determinedthrough negotiation between the source node and the target node.

Optionally, the type of the trigger event may include but is not limitedto any one of the following:

-   -   a first trigger event based on a measurement result of a target        cell;    -   a second trigger event based on a measurement result of a        serving cell;    -   a third trigger event based on a measurement result of a target        cell and a measurement result of a serving cell;    -   a fourth trigger event based on a packet loss rate in data        transmission of a serving cell; and    -   a fifth trigger event based on a latency in data transmission of        a serving cell.

In this implementation, the trigger event based on the measurementresult of the target cell (that is, the first trigger event) may be atrigger event that the measurement result of the target cell satisfies acondition. For example, the measurement result of the target cell isgreater than or equal to a first threshold.

The trigger event based on the measurement result of the serving cell(that is, the second trigger event) may be a trigger event that themeasurement result of the serving cell satisfies a condition. Forexample, the measurement result of the serving cell is less than orequal to a second threshold.

The trigger event based on the measurement result of the target cell andthe measurement result of the serving cell (that is, the third triggerevent) may be a trigger event that the measurement result of the targetcell and the measurement result of the serving cell satisfy a condition.For example, a difference between the measurement result of the targetcell and the measurement result of the serving cell is greater than orequal to a third threshold; or the measurement result of the target cellis greater than or equal to a fourth threshold, and the measurementresult of the serving cell is less than or equal to a fifth threshold.

The trigger event based on the packet loss rate in data transmission ofthe serving cell (that is, the fourth trigger event) may indicate thatthe packet loss rate in data transmission of the serving cell satisfiesa condition. For example, the packet loss rate in data transmission ofthe serving cell is greater than or equal to a sixth threshold.

The trigger event based on the latency in data transmission of theserving cell (that is, the fifth trigger event) may indicate that thelatency in data transmission of the serving cell satisfies a condition.For example, the latency in data transmission of the serving cell isgreater than or equal to a seventh threshold.

It may be understood that the first threshold, the second threshold, thethird threshold, the fourth threshold, the fifth threshold, the sixththreshold, and the seventh threshold are thresholds of the trigger eventconfigured in the configuration information of the trigger event.

The measurement parameter of the trigger event may include but is notlimited to RSRP, RSRQ, SINR, or latency. The trigger type may includeevent trigger or periodic trigger, or the like. The trigger duration isused to indicate that it is considered that a trigger event has occurredonly after duration of the trigger event reaches the trigger duration.For example, it is considered that the trigger event has occurred onlywhen the measurement result of the target cell is greater than or equalto the threshold for duration of 5 ms.

It may be understood that the configuration information of the triggerevent may describe the trigger event. For example, the type of thetrigger event in the configuration information of the trigger event isthat the measurement result of the target cell is greater than or equalto the threshold, the measurement parameter of the trigger event isRSRP, and the threshold of the trigger event is a. In this case, thetrigger event described by the configuration information of the triggerevent may be that a measurement result of RSRP of the target cell isgreater than or equal to a. Therefore, when an evaluated measurementresult of the RSRP of the target cell is greater than or equal to a, itis determined that the trigger event has occurred.

Optionally, the configuration information of the trigger conditionincludes the effective duration of the trigger condition.

In this implementation, the effective duration of the trigger conditionis used to indicate that the trigger condition is effective in theeffective duration, and is not effective beyond the effective duration.

Optionally, the determining, based on the configuration information ofthe at least two trigger events associated with the configurationinformation of the trigger condition, whether the trigger condition issatisfied includes:

-   -   when configuration information of any trigger event in the        configuration information of the at least two trigger events        associated with the configuration information of the trigger        condition is satisfied, determining that the trigger condition        is satisfied; or    -   when configuration information of N trigger events in the        configuration information of the at least two trigger events        associated with the configuration information of the trigger        condition is satisfied, determining that the trigger condition        is satisfied, where N is an integer greater than 1; or    -   when configuration information of all trigger events in the        configuration information of the at least two trigger events        associated with the configuration information of the trigger        condition is satisfied, determining that the trigger condition        is satisfied.

In this implementation, a value of N may be predefined by a protocol orconfigured by the network-side device. Specifically, when the value of Nis configured by the network side, the network-side device may send theconfiguration information of the trigger condition and the configurationinformation of the trigger event together to the terminal device.

This embodiment of this disclosure provides a plurality of manners ofdetermining, based on the configuration information of the at least twotrigger events associated with the configuration information of thetrigger condition, whether the trigger condition is satisfied.Therefore, flexibility of evaluating the trigger condition can beimproved, and accuracy of the decision result can also be improved.

An embodiment of this disclosure further provides a trigger conditionconfiguration method, applied to a source node or a target node. FIG. 4is a flowchart of a trigger condition configuration method according toan embodiment of this disclosure. As shown in FIG. 4 , the methodincludes the following steps.

Step 401: Obtain configuration information of a trigger condition andconfiguration information of a trigger event.

In this embodiment of this disclosure, the configuration information ofthe trigger condition may include but is not limited to effectiveduration of the trigger condition. The configuration information of thetrigger event may include but is not limited to at least one of a typeof the trigger event (for example, a trigger event based on ameasurement result of a target cell, a trigger event based on ameasurement result of a serving cell, or a trigger event based on apacket loss rate in data transmission of a serving cell), a measurementparameter of the trigger event (such as reference signal received power(RSRP), reference signal received quality (RSRQ), a signal tointerference plus noise ratio (SINR), or a latency), and a threshold ofthe trigger event.

Optionally, the configuration information of the trigger condition andthe configuration information of the trigger event may be determinedthrough negotiation between the target node and the source node.

Specifically, when the method is applied to the source node, the sourcenode may negotiate with one or more target nodes to determine theconfiguration information of the trigger condition and the configurationinformation of the trigger event. When the method is applied to thetarget node, the target node may negotiate with the source node todetermine the configuration information of the trigger condition and theconfiguration information of the trigger event.

Step 402: Send the configuration information of the trigger conditionand the configuration information of the trigger event to a terminaldevice, where an association relationship exists between theconfiguration information of the trigger condition and the configurationinformation of the trigger event, and configuration information of onetrigger condition is associated with configuration information of atleast two trigger events.

In this implementation, the configuration information of the triggercondition and the configuration information of the trigger event may besent by using an RRC message. Certainly, the message is not limited inthis embodiment of this disclosure. For example, the message may also beanother downlink message.

It may be understood that a network-side device (such as the target nodeor the source node) may send the configuration information of thetrigger condition and the configuration information of the trigger eventto the terminal device separately by using different RRC messages, ormay send the configuration information of the trigger condition and theconfiguration information of the trigger event to the terminal device byusing a same RRC message.

The configuration information of the trigger condition may includeconfiguration information of one or more trigger conditions, andconfiguration information of each trigger condition is associated withconfiguration information of at least two trigger events.

Optionally, when the method is applied to the source node, the sendingthe configuration information of the trigger condition and theconfiguration information of the trigger event to a terminal deviceincludes:

-   -   when receiving configuration information of a target cell that        is sent by the target node, sending the configuration        information of the trigger condition and the configuration        information of the trigger event to the terminal device; or    -   when receiving the configuration information of the trigger        condition and the configuration information of the trigger event        that are sent by the target node, sending the configuration        information of the trigger condition and the configuration        information of the trigger event to the terminal device.

In this implementation, the configuration information of the triggercondition and the configuration information of the trigger event may besent to the terminal device through the source node. For example, whenreceiving the configuration information of the target cell that is sentby the target node, the source node may associate the configurationinformation of the trigger condition with the configuration informationof the trigger event, and send the associated configuration informationof the trigger condition and configuration information of the triggerevent to the terminal device. In addition, after receiving theconfiguration information of the trigger condition and the configurationinformation of the trigger event that are sent by the target node, thesource node may also send, to the terminal device, the configurationinformation of the trigger condition and the configuration informationof the trigger event that are sent by the target node and received bythe source node.

Optionally, when the method is applied to the target node, the sendingthe configuration information of the trigger condition and theconfiguration information of the trigger event to a terminal deviceincludes:

when receiving request information that is sent by the source node forcondition-triggered cell management, sending the configurationinformation of the trigger condition and the configuration informationof the trigger event to the terminal device through the source node.

In this implementation, the configuration information of the triggercondition and the configuration information of the trigger event thatare sent by the target node to the terminal device through the sourcenode may be received. For example, when receiving the requestinformation that is sent by the source node for cell managementtriggered based on the condition, the target node may associate theconfiguration information of the trigger condition with theconfiguration information of the trigger event, and send the associatedconfiguration information of the trigger condition and configurationinformation of the trigger event to the source node, so that theassociated configuration information of the trigger condition andconfiguration information of the trigger event are sent to the terminaldevice through the source node.

Optionally, in some implementations, a conditional handover (CHO) isdefined as a handover that is executed by a UE when one or more handoverexecution conditions are met. The UE starts evaluating the executioncondition(s) upon receiving CHO configuration, and stops evaluating theexecution condition(s) once a handover is executed (legacy handover orconditional handover execution).

The following principle applies to CHO:

The CHO configuration contains configuration of CHO candidate cell(s)generated by candidate gNB(s) and execution condition(s) generated by asource gNB.

It should be noted that the source node and the target node may be asource base station and a target base station respectively in a cellhandover procedure, or a source SN and a target SN in DC, or a source MNand a target SN in DC, or the like. This is not limited in thisembodiment of this disclosure.

The cell management may include cell handover in conditional handover,or SN addition, change, release, or modification triggered by an MN in aDC architecture, or SN addition, change, release, or modificationtriggered by an SN in a DC architecture, or the like.

For example, the configuration information of the trigger event may bestored in a trigger event information list, each entry in the triggerevent information list includes configuration information of a triggerevent and identification information corresponding to the configurationinformation of the trigger event. The identification information in thetrigger event information list may be measurement identification(MeasID), and if event(s) associated to all measId(s) within conditionaltrigger configuration (condTriggerConfig) for a target candidate cellwithin the stored cell configuration (condRRCReconfig) are fulfilled,then the target candidate cell within the stored condRRCReconfig,associated to that conditional reconfiguration identification(condReconfigId), is considered as a triggered cell, or, the conditionalreconfiguration execution is initiated.

In the trigger condition configuration method in this embodiment of thisdisclosure, configuration information of a trigger condition andconfiguration information of a trigger event are obtained, and theconfiguration information of the trigger condition and the configurationinformation of the trigger event are sent to a terminal device, where anassociation relationship exists between the configuration information ofthe trigger condition and the configuration information of the triggerevent, and configuration information of one trigger condition isassociated with configuration information of at least two triggerevents. Therefore, the terminal device may evaluate the triggercondition based on the configuration information of the at least twotrigger events associated with the configuration information of thetrigger condition, to decide whether to initiate an RRC procedure forcell management. This not only standardizes how a trigger condition isconfigured for a condition-triggered cell management procedure, but alsomakes a decision result more accurate.

Optionally, the configuration information of the trigger condition isstored in a trigger condition information list, the configurationinformation of the trigger event is stored in a trigger eventinformation list, and the association relationship is stored in anassociation relationship list; or

the configuration information of the trigger condition and theconfiguration information of the trigger event are stored in a triggercondition configuration information list, where each entry in thetrigger condition configuration information list includes configurationinformation of a trigger condition and configuration information of atleast two trigger events corresponding to the configuration informationof the trigger condition.

In some implementations, the trigger condition configuration informationlist may be CondReconfigToAddModList, the configuration information ofthe trigger event may be condExecutionCond, each entry in the triggercondition configuration information list may be equivalent toCondReconfigToAddMod, and each entry in the trigger conditionconfiguration information list may include configuration information ofa trigger condition and configuration information of at least twotrigger events corresponding to the configuration information of thetrigger condition. The configuration information of the triggercondition may be equivalent to condReconfigId, and association with thecorresponding configuration information of at least two trigger eventsmay be implemented via condExecutionCond.

In an implementation, the configuration information of the triggercondition, the configuration information of the trigger event, and theassociation relationship between the configuration information of thetrigger condition and the configuration information of the trigger eventare separately stored in different lists. Each entry in the triggercondition information list may include configuration information of onetrigger condition, each entry in the trigger event information list mayinclude configuration information of one trigger event, and each entryin the association relationship list may include one associationrelationship.

It may be understood that because configuration information of onetrigger condition is associated with configuration information of atleast two trigger events in this embodiment of this disclosure, anassociation relationship includes an association relationship betweenconfiguration information of one trigger condition and configurationinformation of at least two trigger events. To be specific, each entryin the association relationship list includes an associationrelationship between configuration information of one trigger conditionand configuration information of at least two trigger events.

Optionally, each entry in the trigger condition information listincludes configuration information of a trigger condition andidentification information corresponding to the configurationinformation of the trigger condition; and

each entry in the trigger event information list includes configurationinformation of a trigger event and identification informationcorresponding to the configuration information of the trigger event.

In this implementation, each entry in the trigger condition informationlist may include identification information in addition to configurationinformation of a trigger condition. For example, each entry in thetrigger condition information list includes configuration information ofa trigger condition and identification information (such as a conditionID) corresponding to the configuration information of the triggercondition. Therefore, the configuration information of the triggercondition may be identified by using the identification informationcorresponding to the configuration information of the trigger condition,or the configuration information of the trigger condition and theconfiguration information of the trigger event are associated by usingthe identification information.

Likewise, each entry in the trigger event information list may includeidentification information in addition to configuration information of atrigger event. For example, each entry in the trigger event informationlist includes configuration information of a trigger event andidentification information (such as an event ID) corresponding to theconfiguration information of the trigger event. Therefore, theconfiguration information of the trigger event may be identified byusing the identification information corresponding to the configurationinformation of the trigger event, or the configuration information ofthe trigger event and the configuration information of the triggercondition are associated by using the identification information.

Optionally, the association relationship includes:

-   -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and an entry tag of the trigger event information        list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information        corresponding to configuration information of a trigger event;        or    -   an association relationship between an entry tag of the trigger        condition information list and an entry tag of the trigger event        information list; or    -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and identification information in the trigger event        information list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information in the        trigger event information list.

In some implementations, the association relationship between theidentification information corresponding to the configurationinformation of the trigger condition and the identification informationin the trigger event information list may include:

an association relationship between the identification informationcorresponding to the configuration information of the trigger conditionand identification information corresponding to configurationinformation of a trigger event.

The identification information in the trigger event information list maybe measurement identification (MeaslD), or target terminalidentification, or event identification, etc.

In this implementation, an entry tag may be an entry in a list. Forexample, a first entry in the list is a tag 1, and a second entry in thelist is a tag 2.

By using a plurality of association relationships provided in thisembodiment of this disclosure, configuration information of a triggercondition may be flexibly associated with configuration information of atrigger event, so that flexibility is improved.

In another implementation, the configuration information of the triggercondition and the configuration information of the trigger event may becorrespondingly stored in a same list. Each entry in the triggercondition configuration information list includes configurationinformation of a trigger condition and configuration information of atleast two trigger events corresponding to the configuration informationof the trigger condition. Therefore, configuration information of atrigger condition can be associated with configuration information of atrigger event by using one list, a more flexible configuration of anassociation between configuration information of a trigger condition andconfiguration information of a trigger event can be implemented, andsignaling transmission overheads can be reduced.

Optionally, the configuration information of the trigger event includesat least one of the following: the type of the trigger event, themeasurement parameter of the trigger event, the threshold of the triggerevent, a trigger type, and trigger duration.

In this implementation, the type of the trigger event, the measurementparameter of the trigger event, the threshold of the trigger event, thetrigger type, the trigger duration, and the like may be all determinedthrough negotiation between the source node and the target node.

Optionally, the type of the trigger event includes any one of thefollowing:

-   -   a first trigger event based on a measurement result of a target        cell;    -   a second trigger event based on a measurement result of a        serving cell;    -   a third trigger event based on a measurement result of a target        cell and a measurement result of a serving cell;    -   a fourth trigger event based on a packet loss rate in data        transmission of a serving cell; and    -   a fifth trigger event based on a latency in data transmission of        a serving cell.

In this implementation, the trigger event based on the measurementresult of the target cell (that is, the first trigger event) may be atrigger event that the measurement result of the target cell satisfies acondition. For example, the measurement result of the target cell isgreater than or equal to a first threshold.

The trigger event based on the measurement result of the serving cell(that is, the second trigger event) may be a trigger event that themeasurement result of the serving cell satisfies a condition. Forexample, the measurement result of the serving cell is less than orequal to a second threshold.

The trigger event based on the measurement result of the target cell andthe measurement result of the serving cell (that is, the third triggerevent) may be a trigger event that the measurement result of the targetcell and the measurement result of the serving cell satisfy a condition.For example, a difference between the measurement result of the targetcell and the measurement result of the serving cell is greater than orequal to a third threshold; or the measurement result of the target cellis greater than or equal to a fourth threshold, and the measurementresult of the serving cell is less than or equal to a fifth threshold.

The trigger event based on the packet loss rate in data transmission ofthe serving cell (that is, the fourth trigger event) may indicate thatthe packet loss rate in data transmission of the serving cell satisfiesa condition. For example, the packet loss rate in data transmission ofthe serving cell is greater than or equal to a sixth threshold.

The trigger event based on the latency in data transmission of theserving cell (that is, the fifth trigger event) may indicate that thelatency in data transmission of the serving cell satisfies a condition.For example, the latency in data transmission of the serving cell isgreater than or equal to a seventh threshold.

It may be understood that the first threshold, the second threshold, thethird threshold, the fourth threshold, the fifth threshold, the sixththreshold, and the seventh threshold are thresholds of the trigger eventconfigured in the configuration information of the trigger event.

The measurement parameter of the trigger event may include but is notlimited to RSRP, RSRQ, SINR, or latency. The trigger type may includeevent trigger or periodic trigger, or the like. The trigger duration isused to indicate that it is considered that a trigger event has occurredonly after duration of the trigger event reaches the trigger duration.For example, it is considered that the trigger event has occurred onlywhen the measurement result of the target cell is greater than or equalto the threshold for duration of 5 ms.

It may be understood that the configuration information of the triggerevent may describe the trigger event. For example, the type of thetrigger event in the configuration information of the trigger event isthat the measurement result of the target cell is greater than or equalto the threshold, the measurement parameter of the trigger event isRSRP, and the threshold of the trigger event is a. In this case, thetrigger event described by the configuration information of the triggerevent may be that a measurement result of RSRP of the target cell isgreater than or equal to a. Therefore, when an evaluated measurementresult of the RSRP of the target cell is greater than or equal to a, itis determined that the trigger event has occurred.

FIG. 5 is a schematic diagram of a cell management method according toanother embodiment of this disclosure. A source node and a target nodein FIG. 5 may be a source base station and a target base station in ahandover procedure, or a source SN and a target SN in DC, or a source MNand a target SN in DC. As shown in FIG. 5 , the method includes thefollowing steps.

Step 501: A source node and a target node negotiate configurationinformation of a trigger condition, configuration information of atrigger event, and configuration information of a target cell forconditional cell management.

The configuration information of the trigger event may include but isnot limited to:

-   -   a type of the trigger event;    -   a measurement parameter of the trigger event, for example, RSRP,        RSRQ, SINR, or latency;    -   a threshold of the trigger event;    -   a trigger type, for example, event trigger or periodic trigger;        and    -   trigger duration, where for example, it is determined that the        trigger event has really triggered only when a measurement        result of a target cell reaches or exceeds a threshold for        duration of 5 ms.

The type of the trigger event may include but is not limited to any oneof the following:

-   -   a measurement result of a target cell reaches or exceeds a        threshold;    -   a measurement result of a serving cell reaches or is lower than        a threshold;    -   a difference between a measurement result of a target cell and a        measurement result of a serving cell reaches or exceeds a        threshold;    -   a measurement result of a target cell reaches or exceeds a first        threshold, and a measurement result of a serving cell reaches or        is lower than a second threshold;    -   a packet loss rate in data transmission of a serving cell        reaches or exceeds a threshold; and    -   a latency in data transmission of a serving cell reaches or        exceeds a threshold.

The configuration information of the trigger condition may includeeffective duration of the trigger condition.

Step 502: After the source node receives, from one or more target nodes,configuration information of one or more condition-triggered targetcells, the source node sends, to a terminal, an RRC message where theconfiguration information of the trigger condition is associated withthe configuration information of the trigger event and the configurationinformation of the target cell. A method for associating theconfiguration information of the trigger condition and the configurationinformation of the trigger event configured in the RRC message may be asfollows:

Method 1: (Multi-List Association)

The configuration includes the following lists:

-   -   a trigger event information list;    -   a trigger condition information list; and    -   an association relationship list.

Each entry in the trigger event information list includes configurationinformation of a trigger event for conditional cell management, and mayfurther include identification information (such as an event ID)corresponding to the configuration information of the trigger event.

Each entry in the trigger condition information list includesconfiguration information of a trigger condition for conditional cellmanagement, and may further include identification information (such asa condition ID) corresponding to the configuration information of thetrigger condition.

The association relationship list is used to indicate associationrelationships between configuration information of trigger events andconfiguration information of trigger conditions. Each associationrelationship in the association relationship list may include thefollowing content:

an entry tag (for example, a first entry in the list is “tag 1”) of thetrigger event information list and identification informationcorresponding to configuration information of a trigger condition.

Optionally, the configuration may further include a target cellconfiguration list, and an association relationship list betweenconfiguration information of trigger conditions and configurationinformation of target cells. Each entry in the target cell configurationlist includes configuration information of a target cell for conditionalcell management, and may additionally further include identificationinformation (such as a reconfiguration ID) corresponding to theconfiguration information of the target cell.

Each association relationship in the association relationship listbetween configuration information of trigger conditions andconfiguration information of target cells includes at least one of thefollowing:

-   -   identification information corresponding to configuration        information of a trigger condition and identification        information corresponding to configuration information of a        target cell;    -   identification information corresponding to configuration        information of a trigger condition and an entry tag (for        example, a first entry in the list is “tag 1”) of the target        cell configuration list;    -   an entry tag (for example, a first entry in the list is “tag 1”)        of the trigger condition information list and identification        information corresponding to configuration information of a        target cell; and an entry tag (for example, a first entry in the        list is “tag 1”) of the trigger    -   condition information list and an entry tag (for example, a        first entry in the list is “tag 1”) of the target cell        configuration list.

Method 2: (Single-List Association, where a Trigger Event and a TriggerCondition are in a Many-to-One Relationship)

The configuration includes the following list:

a trigger condition configuration information list.

Each entry in the trigger condition configuration information listincludes configuration information of one trigger condition forconditional cell management and configuration information of a pluralityof trigger events corresponding to the configuration information of thetrigger condition.

Optionally, the configuration may further include a target cellconfiguration information list, where each entry in the target cellconfiguration information list may include any one of the following:

-   -   configuration information of one trigger condition for        conditional cell management and configuration information of one        target cell;    -   configuration information of one trigger condition for        conditional cell management and configuration information of a        plurality of target cells; and    -   configuration information of a plurality of trigger conditions        for conditional cell management and configuration information of        one target cell.

Optionally, step 502 may also be replaced as follows: After receivingone or more pieces of request information that are sent by the sourcenode for condition-triggered cell management, the target node sends anRRC message that has associated the configuration information of thetrigger event, the configuration information of the trigger condition,and the configuration information of the target cell to the UE. A methodfor associating the configuration information of the trigger event andthe configuration information of the trigger condition reconfigured inthe RRC message is the same as the foregoing method, and is notdescribed again herein. The RRC message may be directly delivered by thetarget node to the UE, or may be forwarded by the source node to the UE.

Step 503: The terminal device evaluates the trigger condition based on anetwork-side configuration. The evaluation method includes any one ofthe following:

Method 1 (corresponding to the method 1 in step 502): The UE evaluates acorresponding trigger event in the trigger event information listspecified by the association relationship list.

Method 2 (corresponding to the method 2 in step 502): The UE evaluates atrigger event corresponding to a trigger condition in the triggercondition configuration information list.

Whether the trigger condition is satisfied may be evaluated based on thefollowing evaluation method:

-   -   if any trigger event corresponding to the trigger condition is        satisfied, it is considered that the trigger condition is        satisfied;    -   if a plurality of trigger events corresponding to the trigger        condition are satisfied, it is considered that the trigger        condition is satisfied, where a specific quantity of satisfied        trigger events may be agreed upon based on a protocol or        configured by a network; and    -   if all trigger events corresponding to the trigger condition are        satisfied, it is considered that the trigger condition is        satisfied.

Step 504: When the trigger condition is satisfied, the terminal deviceevaluates whether a target cell configuration is applied.

The evaluation method may include any one of the following:

-   -   if any trigger condition corresponding to the target cell        configuration is satisfied, the target cell configuration is        applied;    -   if a plurality of trigger conditions corresponding to the target        cell configuration are satisfied, the target cell configuration        is applied, where a specific quantity of satisfied trigger        conditions may be agreed upon based on the protocol or        configured by the network; and    -   if all trigger conditions corresponding to the target cell        configuration are satisfied, the target cell configuration is        applied.

In this embodiment of this disclosure, when a manner ofcondition-triggered cell management is used, UE may evaluate a triggercondition based on a plurality of trigger events to further decidewhether to perform a procedure such as cell handover or cell addition orcell deletion or cell change, thereby improving decision accuracy. Forexample, whether to perform handover is evaluated based on a pluralityof trigger events. This can further increase a handover success rate andavoid unnecessary handover, and maximize utilization of networkresources.

FIG. 6 is a structural diagram of a terminal device according to anembodiment of this disclosure. As shown in FIG. 6 , the terminal device600 includes a receiving module 601, a determining module 602, and aninitiation module 603.

The receiving module 601 is configured to receive configurationinformation of a trigger condition and configuration information of atrigger event that are sent by a network-side device, where anassociation relationship exists between the configuration information ofthe trigger condition and the configuration information of the triggerevent, and configuration information of one trigger condition isassociated with configuration information of at least two triggerevents.

The determining module 602 is configured to determine, based on theconfiguration information of the at least two trigger events associatedwith the configuration information of the trigger condition, whether thetrigger condition is satisfied.

The initiation module 603 is configured to initiate a radio resourcecontrol RRC procedure for cell management when the trigger condition issatisfied.

Optionally, in some implementations, a conditional handover (CHO) isdefined as a handover that is executed by a UE when one or more handoverexecution conditions are met. The UE starts evaluating the executioncondition(s) upon receiving CHO configuration, and stops evaluating theexecution condition(s) once a handover is executed (legacy handover orconditional handover execution).

The following principle applies to CHO:

The CHO configuration contains configuration of CHO candidate cell(s)generated by candidate gNB(s) and execution condition(s) generated by asource gNB.

For example, the configuration information of the trigger event may bestored in a trigger event information list, each entry in the triggerevent information list includes configuration information of a triggerevent and identification information corresponding to the configurationinformation of the trigger event. The identification information in thetrigger event information list may be measurement identification(MeasID), and if event(s) associated to all measId(s) within conditionaltrigger configuration (condTriggerConfig) for a target candidate cellwithin the stored cell configuration (condRRCReconfig) are fulfilled,then the target candidate cell within the stored condRRCReconfig,associated to that conditional reconfiguration identification(condReconfigId), is considered as a triggered cell, or, the conditionalreconfiguration execution is initiated.

Optionally, the configuration information of the trigger condition isstored in a trigger condition information list, the configurationinformation of the trigger event is stored in a trigger eventinformation list, and the association relationship is stored in anassociation relationship list; or

the configuration information of the trigger condition and theconfiguration information of the trigger event are stored in a triggercondition configuration information list, where each entry in thetrigger condition configuration information list includes configurationinformation of a trigger condition and configuration information of atleast two trigger events corresponding to the configuration informationof the trigger condition.

In some implementations, the trigger condition configuration informationlist may be CondReconfigToAddModList, the configuration information ofthe trigger event may be condExecutionCond, each entry in the triggercondition configuration information list may be equivalent toCondReconfigToAddMod, and each entry in the trigger conditionconfiguration information list may include configuration information ofa trigger condition and configuration information of at least twotrigger events corresponding to the configuration information of thetrigger condition. The configuration information of the triggercondition may be equivalent to condReconfigId, and association with thecorresponding configuration information of at least two trigger eventsmay be implemented via condExecutionCond.

Optionally, each entry in the trigger condition information listincludes configuration information of a trigger condition andidentification information corresponding to the configurationinformation of the trigger condition;

-   -   each entry in the trigger event information list includes        configuration information of a trigger event and identification        information corresponding to the configuration information of        the trigger event; and    -   the association relationship includes:    -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and an entry tag of the trigger event information        list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information        corresponding to configuration information of a trigger event;        or    -   an association relationship between an entry tag of the trigger        condition information list and an entry tag of the trigger event        information list; or    -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and identification information in the trigger event        information list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information in the        trigger event information list.

In some implementations, the association relationship between theidentification information corresponding to the configurationinformation of the trigger condition and the identification informationin the trigger event information list may include:

an association relationship between the identification informationcorresponding to the configuration information of the trigger conditionand identification information corresponding to configurationinformation of a trigger event.

The identification information in the trigger event information list maybe measurement identification (MeasID), or target terminalidentification, or event identification, etc.

Optionally, the configuration information of the trigger event includesat least one of the following: a type of the trigger event, ameasurement parameter of the trigger event, a threshold of the triggerevent, a trigger type, and trigger duration.

Optionally, the type of the trigger event includes any one of thefollowing:

-   -   a first trigger event based on a measurement result of a target        cell;    -   a second trigger event based on a measurement result of a        serving cell;    -   a third trigger event based on a measurement result of a target        cell and a measurement result of a serving cell;    -   a fourth trigger event based on a packet loss rate in data        transmission of a serving cell; and    -   a fifth trigger event based on a latency in data transmission of        a serving cell.

Optionally, the configuration information of the trigger conditionincludes effective duration of the trigger condition.

Optionally, the determining module is specifically configured to:

-   -   when configuration information of any trigger event in the        configuration information of the at least two trigger events        associated with the configuration information of the trigger        condition is satisfied, determine that the trigger condition is        satisfied; or    -   when configuration information of N trigger events in the        configuration information of the at least two trigger events        associated with the configuration information of the trigger        condition is satisfied, determine that the trigger condition is        satisfied, where N is an integer greater than 1; or    -   when configuration information of all trigger events in the        configuration information of the at least two trigger events        associated with the configuration information of the trigger        condition is satisfied, determine that the trigger condition is        satisfied.

Optionally, a value of N may be predefined by a protocol or configuredby the network-side device.

Optionally, the receiving module is specifically configured to:

-   -   receive the configuration information of the trigger condition        and the configuration information of the trigger event that are        sent by a source node; or    -   receive the configuration information of the trigger condition        and the configuration information of the trigger event that are        sent by a target node through a source node.

The terminal device 600 provided in this embodiment of this disclosurecan implement the procedures implemented by the terminal device in themethod embodiments in FIG. 3 and FIG. 5 . To avoid repetition, detailsare not described again herein.

In the terminal device 600 in this embodiment of this disclosure, thereceiving module 601 is configured to receive configuration informationof a trigger condition and configuration information of a trigger eventthat are sent by a network-side device, where an associationrelationship exists between the configuration information of the triggercondition and the configuration information of the trigger event, andconfiguration information of one trigger condition is associated withconfiguration information of at least two trigger events; thedetermining module 602 is configured to determine, based on theconfiguration information of the at least two trigger events associatedwith the configuration information of the trigger condition, whether thetrigger condition is satisfied; and the initiation module 603 isconfigured to initiate a radio resource control RRC procedure for cellmanagement when the trigger condition is satisfied. This not onlystandardizes how a trigger condition is configured for acondition-triggered cell management procedure, but also makes a decisionresult more accurate.

FIG. 7 is a structural diagram of a network-side device according to anembodiment of this disclosure. The network-side device is a source nodeor a target node. As shown in FIG. 7 , the network-side device 700includes an obtaining module 701 and a sending module 702.

The obtaining module 701 is configured to obtain configurationinformation of a trigger condition and configuration information of atrigger event.

The sending module 702 is configured to send the configurationinformation of the trigger condition and the configuration informationof the trigger event to a terminal device, where an associationrelationship exists between the configuration information of the triggercondition and the configuration information of the trigger event, andconfiguration information of one trigger condition is associated withconfiguration information of at least two trigger events.

Optionally, in some implementations, a conditional handover (CHO) isdefined as a handover that is executed by a UE when one or more handoverexecution conditions are met. The UE starts evaluating the executioncondition(s) upon receiving CHO configuration, and stops evaluating theexecution condition(s) once a handover is executed (legacy handover orconditional handover execution).

The following principle applies to CHO:

The CHO configuration contains configuration of CHO candidate cell(s)generated by candidate gNB(s) and execution condition(s) generated by asource gNB.

For example, the configuration information of the trigger event may bestored in a trigger event information list, each entry in the triggerevent information list includes configuration information of a triggerevent and identification information corresponding to the configurationinformation of the trigger event. The identification information in thetrigger event information list may be measurement identification(MeasID), and if event(s) associated to all measld(s) within conditionaltrigger configuration (condTriggerConfig) for a target candidate cellwithin the stored cell configuration (condRRCReconfig) are fulfilled,then the target candidate cell within the stored condRRCReconfig,associated to that conditional reconfiguration identification(condReconfigId), is considered as a triggered cell, or, the conditionalreconfiguration execution is initiated.

Optionally, the configuration information of the trigger condition isstored in a trigger condition information list, the configurationinformation of the trigger event is stored in a trigger eventinformation list, and the association relationship is stored in anassociation relationship list; or

the configuration information of the trigger condition and theconfiguration information of the trigger event are stored in a triggercondition configuration information list, where each entry in thetrigger condition configuration information list includes configurationinformation of a trigger condition and configuration information of atleast two trigger events corresponding to the configuration informationof the trigger condition.

In some implementations, the trigger condition configuration informationlist may be CondReconfigToAddModList, the configuration information ofthe trigger event may be condExecutionCond, each entry in the triggercondition configuration information list may be equivalent toCondReconfigToAddMod, and each entry in the trigger conditionconfiguration information list may include configuration information ofa trigger condition and configuration information of at least twotrigger events corresponding to the configuration information of thetrigger condition. The configuration information of the triggercondition may be equivalent to condReconfigId, and association with thecorresponding configuration information of at least two trigger eventsmay be implemented via condExecutionCond.

Optionally, each entry in the trigger condition information listincludes configuration information of a trigger condition andidentification information corresponding to the configurationinformation of the trigger condition;

-   -   each entry in the trigger event information list includes        configuration information of a trigger event and identification        information corresponding to the configuration information of        the trigger event; and    -   the association relationship includes:    -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and an entry tag of the trigger event information        list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information        corresponding to configuration information of a trigger event;        or    -   an association relationship between an entry tag of the trigger        condition information list and an entry tag of the trigger event        information list; or    -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and identification information in the trigger event        information list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information in the        trigger event information list.

In some implementations, the association relationship between theidentification information corresponding to the configurationinformation of the trigger condition and the identification informationin the trigger event information list may include:

an association relationship between the identification informationcorresponding to the configuration information of the trigger conditionand identification information corresponding to configurationinformation of a trigger event.

The identification information in the trigger event information list maybe measurement identification (MeasID), or target terminalidentification, or event identification, etc.

Optionally, the configuration information of the trigger event includesat least one of the following: a type of the trigger event, ameasurement parameter of the trigger event, a threshold of the triggerevent, a trigger type, and trigger duration.

Optionally, the type of the trigger event includes any one of thefollowing:

-   -   a first trigger event based on a measurement result of a target        cell;    -   a second trigger event based on a measurement result of a        serving cell;    -   a third trigger event based on a measurement result of a target        cell and a measurement result of a serving cell;    -   a fourth trigger event based on a packet loss rate in data        transmission of a serving cell; and    -   a fifth trigger event based on a latency in data transmission of        a serving cell.

Optionally, the configuration information of the trigger conditionincludes effective duration of the trigger condition.

Optionally, when the network-side device is the source node, the sendingmodule is specifically configured to:

-   -   when configuration information of a target cell that is sent by        the target node is received, send the configuration information        of the trigger condition and the configuration information of        the trigger event to the terminal device; or    -   when the configuration information of the trigger condition and        the configuration information of the trigger event that are sent        by the target node are received, send the configuration        information of the trigger condition and the configuration        information of the trigger event to the terminal device.

Optionally, when the network-side device is the target node, the sendingmodule is specifically configured to:

when request information that is sent by the source node forcondition-triggered cell management is received, send the configurationinformation of the trigger condition and the configuration informationof the trigger event to the terminal device through the source node.

Optionally, the configuration information of the trigger condition andthe configuration information of the trigger event are determinedthrough negotiation between the target node and the source node.

The network-side device 700 provided in this embodiment of thisdisclosure can implement the procedures implemented by the network-sidedevice in the method embodiments in FIG. 4 and FIG. 5 . To avoidrepetition, details are not described again herein.

In the network-side device 700 in this embodiment of this disclosure,the obtaining module 701 is configured to obtain configurationinformation of a trigger condition and configuration information of atrigger event; and the sending module 702 is configured to send theconfiguration information of the trigger condition and the configurationinformation of the trigger event to a terminal device, where anassociation relationship exists between the configuration information ofthe trigger condition and the configuration information of the triggerevent, and configuration information of one trigger condition isassociated with configuration information of at least two triggerevents. Therefore, the terminal device may evaluate the triggercondition based on the configuration information of the at least twotrigger events associated with the configuration information of thetrigger condition, to decide whether to initiate an RRC procedure forcell management. This not only standardizes how a trigger condition isconfigured for a condition-triggered cell management procedure, but alsomakes a decision result more accurate.

FIG. 8 is a structural diagram of a terminal device according to anotherembodiment of this disclosure. Referring to FIG. 8 , the terminal device800 includes but is not limited to components such as a radio frequencyunit 801, a network module 802, an audio output unit 803, an input unit804, a sensor 805, a display unit 806, a user input unit 807, aninterface unit 808, a memory 809, a processor 810, and a power supply811. A person skilled in the art may understand that the structure ofthe terminal device shown in FIG. 8 does not constitute a limitation onthe terminal device. A quantity of components included in the terminaldevice may be greater or less than that shown in the figure, or somecomponents are combined, or component arrangements are different. Inthis implementation, the terminal device includes but is not limited toa mobile phone, a tablet computer, a notebook computer, a palmtopcomputer, an in-vehicle terminal, a wearable device, a pedometer, or thelike.

The radio frequency unit 801 is configured to receive configurationinformation of a trigger condition and configuration information of atrigger event that are sent by a network-side device, where anassociation relationship exists between the configuration information ofthe trigger condition and the configuration information of the triggerevent, and configuration information of one trigger condition isassociated with configuration information of at least two triggerevents.

The processor 810 is configured to determine, based on the configurationinformation of the at least two trigger events associated with theconfiguration information of the trigger condition, whether the triggercondition is satisfied; and initiate a radio resource control RRCprocedure for cell management when the trigger condition is satisfied.

This embodiment of this disclosure not only standardizes how a triggercondition is configured for a condition-triggered cell managementprocedure, but also makes a decision result more accurate by evaluatingthe trigger condition based on the configuration information of the atleast two trigger events associated with the configuration informationof the trigger condition.

Optionally, in some implementations, a conditional handover (CHO) isdefined as a handover that is executed by a UE when one or more handoverexecution conditions are met. The UE starts evaluating the executioncondition(s) upon receiving CHO configuration, and stops evaluating theexecution condition(s) once a handover is executed (legacy handover orconditional handover execution).

The following principle applies to CHO:

The CHO configuration contains configuration of CHO candidate cell(s)generated by candidate gNB(s) and execution condition(s) generated by asource gNB.

For example, the configuration information of the trigger event may bestored in a trigger event information list, each entry in the triggerevent information list includes configuration information of a triggerevent and identification information corresponding to the configurationinformation of the trigger event. The identification information in thetrigger event information list may be measurement identification(MeasID), and if event(s) associated to all measId(s) within conditionaltrigger configuration (condTriggerConfig) for a target candidate cellwithin the stored cell configuration (condRRCReconfig) are fulfilled,then the target candidate cell within the stored condRRCReconfig,associated to that conditional reconfiguration identification(condReconfigId), is considered as a triggered cell, or, the conditionalreconfiguration execution is initiated.

Optionally, the configuration information of the trigger condition isstored in a trigger condition information list, the configurationinformation of the trigger event is stored in a trigger eventinformation list, and the association relationship is stored in anassociation relationship list; or

the configuration information of the trigger condition and theconfiguration information of the trigger event are stored in a triggercondition configuration information list, where each entry in thetrigger condition configuration information list includes configurationinformation of a trigger condition and configuration information of atleast two trigger events corresponding to the configuration informationof the trigger condition.

In some implementations, the trigger condition configuration informationlist may be CondReconfigToAddModList, the configuration information ofthe trigger event may be condExecutionCond, each entry in the triggercondition configuration information list may be equivalent toCondReconfigToAddMod, and each entry in the trigger conditionconfiguration information list may include configuration information ofa trigger condition and configuration information of at least twotrigger events corresponding to the configuration information of thetrigger condition. The configuration information of the triggercondition may be equivalent to condReconfigId, and association with thecorresponding configuration information of at least two trigger eventsmay be implemented via condExecutionCond.

Optionally, each entry in the trigger condition information listincludes configuration information of a trigger condition andidentification information corresponding to the configurationinformation of the trigger condition;

-   -   each entry in the trigger event information list includes        configuration information of a trigger event and identification        information corresponding to the configuration information of        the trigger event; and    -   the association relationship includes:    -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and an entry tag of the trigger event information        list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information        corresponding to configuration information of a trigger event;        or    -   an association relationship between an entry tag of the trigger        condition information list and an entry tag of the trigger event        information list; or    -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and identification information in the trigger event        information list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information in the        trigger event information list.

In some implementations, the association relationship between theidentification information corresponding to the configurationinformation of the trigger condition and the identification informationin the trigger event information list may include:

an association relationship between the identification informationcorresponding to the configuration information of the trigger conditionand identification information corresponding to configurationinformation of a trigger event.

The identification information in the trigger event information list maybe measurement identification (MeasID), or target terminalidentification, or event identification, etc.

Optionally, the configuration information of the trigger event includesat least one of the following: a type of the trigger event, ameasurement parameter of the trigger event, a threshold of the triggerevent, a trigger type, and trigger duration.

Optionally, the type of the trigger event includes any one of thefollowing:

-   -   a first trigger event based on a measurement result of a target        cell;    -   a second trigger event based on a measurement result of a        serving cell;    -   a third trigger event based on a measurement result of a target        cell and a measurement result of a serving cell;    -   a fourth trigger event based on a packet loss rate in data        transmission of a serving cell; and    -   a fifth trigger event based on a latency in data transmission of        a serving cell.

Optionally, the configuration information of the trigger conditionincludes effective duration of the trigger condition.

Optionally, the processor 810 is further configured to:

-   -   when configuration information of any trigger event in the        configuration information of the at least two trigger events        associated with the configuration information of the trigger        condition is satisfied, determine that the trigger condition is        satisfied; or    -   when configuration information of N trigger events in the        configuration information of the at least two trigger events        associated with the configuration information of the trigger        condition is satisfied, determine that the trigger condition is        satisfied, where N is an integer greater than 1; or    -   when configuration information of all trigger events in the        configuration information of the at least two trigger events        associated with the configuration information of the trigger        condition is satisfied, determine that the trigger condition is        satisfied.

Optionally, a value of N may be predefined by a protocol or configuredby the network-side device.

Optionally, the processor 810 is further configured to:

-   -   receive the configuration information of the trigger condition        and the configuration information of the trigger event that are        sent by a source node; or    -   receive the configuration information of the trigger condition        and the configuration information of the trigger event that are        sent by a target node through a source node.

It should be understood that in this implementation, the radio frequencyunit 801 may be configured to receive and send signals in an informationreception or transmission or call process. Specifically, after receivingdownlink data from a base station, the radio frequency unit 801 sendsthe downlink data to the processor 810 for processing, and in addition,sends uplink data to the base station. Generally, the radio frequencyunit 801 includes but is not limited to an antenna, at least oneamplifier, a transceiver, a coupler, a low noise amplifier, a duplexer,and the like. In addition, the radio frequency unit 801 may furthercommunicate with a network and other devices through a wirelesscommunications system.

The terminal device provides wireless broadband Internet access for auser by using the network module 802, for example, helps the user sendand receive e-mails, browse web pages, and access streaming media.

The audio output unit 803 may convert audio data received by the radiofrequency unit 801 or the network module 802 or stored in the memory 809into an audio signal, and output the audio signal as a sound. Inaddition, the audio output unit 803 may further provide an audio output(for example, a call signal reception sound or a message receptionsound) related to a specific function performed by the terminal device800. The audio output unit 803 includes a speaker, a buzzer, a telephonereceiver, and the like.

The input unit 804 is configured to receive an audio or video signal.The input unit 804 may include a graphics processing unit (GPU) 8041 anda microphone 8042. The graphics processing unit 8041 processes imagedata of a still picture or a video obtained by an image captureapparatus (for example, a camera) in an image capture mode or a videocapture mode. A processed image frame may be displayed on the displayunit 806. An image frame processed by the graphics processing unit 8041may be stored in the memory 809 (or other storage media) or sent by theradio frequency unit 801 or the network module 802. The microphone 8042can receive a sound and can process the sound into audio data. Theprocessed audio data may be converted in a telephone call mode into aformat that can be sent by the radio frequency unit 801 to a mobilecommunications base station, for outputting.

The terminal device 800 further includes at least one sensor 805, forexample, a light sensor, a motion sensor, and other sensors.Specifically, the light sensor includes an ambient light sensor and aproximity sensor. The ambient light sensor may adjust luminance of adisplay panel 8061 based on brightness of ambient light. The proximitysensor may turn off and/or backlight the display panel 8061 when theterminal device 800 moves to an ear. As a type of motion sensor, anaccelerometer sensor may detect acceleration magnitudes in alldirections (generally three axes), and when the accelerometer sensor isstationary, may detect a magnitude and a direction of gravity, and maybe configured for terminal device posture recognition (such as switchingbetween landscape and portrait, related games, and magnetometer posturecalibration), vibration recognition related functions (such as apedometer and stroke), and the like. The sensor 805 may further includea fingerprint sensor, a pressure sensor, an iris sensor, a molecularsensor, a gyroscope, a barometer, a hygrometer, a thermometer, aninfrared sensor, or the like. Details are not described herein.

The display unit 806 is configured to display information input by theuser or information provided for the user. The display unit 806 mayinclude the display panel 8061. The display panel 8061 may be configuredin a form of a liquid crystal display (LCD), an organic light-emittingdiode (OLED), or the like.

The user input unit 807 may be configured to receive input digit orcharacter information, and generate a key signal input related to usersettings and function control of the terminal device. Specifically, theuser input unit 807 includes a touch panel 8071 and other input devices8072. The touch panel 8071, also referred to as a touchscreen, maycapture a touch operation performed by the user on or near the touchpanel (for example, an operation performed by the user on the touchpanel 8071 or near the touch panel 8071 by using any appropriate objector accessory such as a finger or a stylus). The touch panel 8071 mayinclude two parts: a touch detection apparatus and a touch controller.The touch detection apparatus detects a touch direction of the user,detects a signal carried by a touch operation, and transmits the signalto the touch controller. The touch controller receives touch informationfrom the touch detection apparatus, converts the touch information intopoint coordinates, sends the point coordinates to the processor 810, andreceives and executes a command sent by the processor 810. In addition,the touch panel 8071 may be implemented in a plurality of forms, forexample, a resistive, capacitive, infrared, or surface acoustic wavetouch panel. The user input unit 807 may further include the other inputdevices 8072 in addition to the touch panel 8071. Specifically, theother input devices 8072 may include but are not limited to a physicalkeyboard, a function key (such as a volume control key or a power on/offkey), a trackball, a mouse, a joystick, and the like. Details are notdescribed herein.

Further, the touch panel 8071 may cover the display panel 8061. Afterthe touch panel 8071 detects a touch operation on or near the touchpanel, the touch panel 8071 transmits the touch operation to theprocessor 810 to determine a type of a touch event. Then the processor810 provides a corresponding visual output on the display panel 8061based on the type of the touch event. Although the touch panel 8071 andthe display panel 8061 are used as two independent components toimplement input and output functions of the terminal device in FIG. 8 ,the touch panel 8071 and the display panel 8061 may be integrated toimplement the input and output functions of the terminal device in someembodiments. This is not specifically limited herein.

The interface unit 808 is an interface for connecting an externalapparatus to the terminal device 800. For example, the externalapparatus may include a wired or wireless headphone port, an externalpower (or battery charger) port, a wired or wireless data port, a memorycard port, a port for connecting an apparatus having an identificationmodule, an audio input/output (I/O) port, a video I/O port, an earphoneport, and the like. The interface unit 808 may be configured to receivean input (for example, data information or power) from an externalapparatus, and transmit the received input to one or more components inthe terminal device 800, or may be configured to transmit data betweenthe terminal device 800 device and an external apparatus.

The memory 809 may be configured to store a software program and variousdata. The memory 809 may mainly include a program storage area and adata storage area. The program storage area may store an operatingsystem, an application program required for at least one function (suchas a sound play function and an image play function), and the like. Thedata storage area may store data created based on use of the mobilephone (such as audio data and a phone book), and the like. In addition,the memory 809 may include a high-speed random access memory, or mayinclude a non-volatile memory, for example, at least one magnetic diskstorage device, a flash memory, or other non-volatile solid-statestorage devices.

The processor 810 is a control center of the terminal device. Theprocessor 810 uses various interfaces and lines to connect all parts ofthe entire terminal device, and performs various functions and dataprocessing of the terminal device by running or executing softwareprograms and/or modules stored in the memory 809 and calling data storedin the memory 809, thereby performing overall monitoring on the terminaldevice. The processor 810 may include one or more processing units.Optionally, the processor 810 may integrate an application processor anda modem processor. The application processor mainly processes theoperating system, user interface, application program, and the like. Themodem processor mainly processes wireless communication. It may beunderstood that the modem processor may alternatively not be integratedinto the processor 810.

The terminal device 800 may further include the power supply 811 (suchas a battery) supplying power to each component. Optionally, the powersupply 811 may be logically connected to the processor 810 by using apower management system, so that functions such as charge and dischargemanagement and power consumption management are implemented by using thepower management system.

In addition, the terminal device 800 includes some functional modulesthat are not illustrated. Details are not described herein.

Optionally, an embodiment of this disclosure further provides a terminaldevice, including a processor 810, a memory 809, and a computer programstored in the memory 809 and capable of running on the processor 810.When the computer program is executed by the processor 810, theprocedures of the foregoing embodiment of the cell management method areimplemented, and a same technical effect can be achieved. To avoidrepetition, details are not described again herein.

An embodiment of this disclosure further provides a computer-readablestorage medium, where the computer-readable storage medium stores acomputer program. When the computer program is executed by a processor,the procedures of the foregoing embodiment of the cell management methodare implemented, and a same technical effect can be achieved. To avoidrepetition, details are not described again herein. Thecomputer-readable storage medium is, for example, a read-only memory(ROM), a random access memory (RAM), a magnetic disk, or an opticaldisc.

FIG. 9 is a structural diagram of a network-side device according toanother embodiment of this disclosure. The network-side device may be asource node or a target node. As shown in FIG. 9 , the network-sidedevice 900 includes a processor 901, a memory 902, a bus interface 903,and a transceiver 904, where the processor 901, the memory 902, and thetransceiver 904 are all connected to the bus interface 903.

In this embodiment of this disclosure, the network-side device 900further includes a computer program stored in the memory 902 and capableof running on the processor 901. When the computer program is executedby the processor 901, the following steps are implemented:

-   -   obtaining configuration information of a trigger condition and        configuration information of a trigger event; and    -   sending the configuration information of the trigger condition        and the configuration information of the trigger event to a        terminal device, where an association relationship exists        between the configuration information of the trigger condition        and the configuration information of the trigger event, and        configuration information of one trigger condition is associated        with configuration information of at least two trigger events.

Optionally, in some implementations, a conditional handover (CHO) isdefined as a handover that is executed by a UE when one or more handoverexecution conditions are met. The UE starts evaluating the executioncondition(s) upon receiving CHO configuration, and stops evaluating theexecution condition(s) once a handover is executed (legacy handover orconditional handover execution).

The following principle applies to CHO:

The CHO configuration contains configuration of CHO candidate cell(s)generated by candidate gNB(s) and execution condition(s) generated by asource gNB.

For example, the configuration information of the trigger event may bestored in a trigger event information list, each entry in the triggerevent information list includes configuration information of a triggerevent and identification information corresponding to the configurationinformation of the trigger event. The identification information in thetrigger event information list may be measurement identification(MeasID), and if event(s) associated to all measId(s) within conditionaltrigger configuration (condTriggerConfig) for a target candidate cellwithin the stored cell configuration (condRRCReconfig) are fulfilled,then the target candidate cell within the stored condRRCReconfig,associated to that conditional reconfiguration identification(condReconfigId), is considered as a triggered cell, or, the conditionalreconfiguration execution is initiated.

Optionally, the configuration information of the trigger condition isstored in a trigger condition information list, the configurationinformation of the trigger event is stored in a trigger eventinformation list, and the association relationship is stored in anassociation relationship list; or

the configuration information of the trigger condition and theconfiguration information of the trigger event are stored in a triggercondition configuration information list, where each entry in thetrigger condition configuration information list includes configurationinformation of a trigger condition and configuration information of atleast two trigger events corresponding to the configuration informationof the trigger condition.

In some implementations, the trigger condition configuration informationlist may be CondReconfigToAddModList, the configuration information ofthe trigger event may be condExecutionCond, each entry in the triggercondition configuration information list may be equivalent toCondReconfigToAddMod, and each entry in the trigger conditionconfiguration information list may include configuration information ofa trigger condition and configuration information of at least twotrigger events corresponding to the configuration information of thetrigger condition. The configuration information of the triggercondition may be equivalent to condReconfigId, and association with thecorresponding configuration information of at least two trigger eventsmay be implemented via condExecutionCond.

Optionally, each entry in the trigger condition information listincludes configuration information of a trigger condition andidentification information corresponding to the configurationinformation of the trigger condition;

each entry in the trigger event information list includes configurationinformation of a trigger event and identification informationcorresponding to the configuration information of the trigger event; and

-   -   the association relationship includes:    -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and an entry tag of the trigger event information        list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information        corresponding to configuration information of a trigger event;        or    -   an association relationship between an entry tag of the trigger        condition information list and an entry tag of the trigger event        information list; or    -   an association relationship between identification information        corresponding to configuration information of a trigger        condition and identification information in the trigger event        information list; or    -   an association relationship between an entry tag of the trigger        condition information list and identification information in the        trigger event information list.

In some implementations, the association relationship between theidentification information corresponding to the configurationinformation of the trigger condition and the identification informationin the trigger event information list may include:

an association relationship between the identification informationcorresponding to the configuration information of the trigger conditionand identification information corresponding to configurationinformation of a trigger event.

The identification information in the trigger event information list maybe measurement identification (MeasID), or target terminalidentification, or event identification, etc.

Optionally, the configuration information of the trigger event includesat least one of the following: a type of the trigger event, ameasurement parameter of the trigger event, a threshold of the triggerevent, a trigger type, and trigger duration.

Optionally, the type of the trigger event includes any one of thefollowing:

-   -   a first trigger event based on a measurement result of a target        cell;    -   a second trigger event based on a measurement result of a        serving cell;    -   a third trigger event based on a measurement result of a target        cell and a measurement result of a serving cell;    -   a fourth trigger event based on a packet loss rate in data        transmission of a serving cell; and    -   a fifth trigger event based on a latency in data transmission of        a serving cell.

Optionally, the configuration information of the trigger conditionincludes effective duration of the trigger condition.

Optionally, when the method is applied to the source node, when thecomputer program is executed by the processor 901, the following stepmay be further implemented:

-   -   when receiving configuration information of a target cell that        is sent by the target node, sending the configuration        information of the trigger condition and the configuration        information of the trigger event to the terminal device; or    -   when receiving the configuration information of the trigger        condition and the configuration information of the trigger event        that are sent by the target node, sending the configuration        information of the trigger condition and the configuration        information of the trigger event to the terminal device.

Optionally, when the method is applied to the target node, when thecomputer program is executed by the processor 901, the following stepmay be further implemented:

when receiving request information that is sent by the source node forcondition-triggered cell management, sending the configurationinformation of the trigger condition and the configuration informationof the trigger event to the terminal device through the source node.

Optionally, the configuration information of the trigger condition andthe configuration information of the trigger event are determinedthrough negotiation between the target node and the source node.

An embodiment of this disclosure further provides a network-side device,including a processor 901, a memory 902, and a computer program storedin the memory 902 and capable of running on the processor 901. When thecomputer program is executed by the processor 901, the procedures of theforegoing embodiment of the trigger condition configuration method areimplemented, and a same technical effect can be achieved. To avoidrepetition, details are not described again herein.

An embodiment of this disclosure further provides a computer-readablestorage medium, where the computer-readable storage medium stores acomputer program. When the computer program is executed by a processor,the procedures of the foregoing embodiment of the trigger conditionconfiguration method are implemented, and a same technical effect can beachieved. To avoid repetition, details are not described again herein.The computer-readable storage medium is, for example, a read-only memory(ROM), a random access memory (RAM), a magnetic disk, or an opticaldisc.

It should be noted that in this specification, the term “comprise”,“include”, or any of their variants is intended to cover a non-exclusiveinclusion, so that a process, a method, an article, or an apparatus thatincludes a list of elements not only includes those elements but alsoincludes other elements that are not expressly listed, or furtherincludes elements inherent to such process, method, article, orapparatus. In absence of more constraints, an element preceded by“includes a . . . ” does not preclude the existence of other identicalelements in the process, method, article, or apparatus that includes theelement.

According to the description of the foregoing implementations, a personskilled in the art can clearly understand that the method in theforegoing embodiments may be implemented by software in addition to anecessary universal hardware platform or by hardware only. In mostcases, the former is a more preferred implementation. Based on such anunderstanding, the technical solutions of this disclosure essentially,or the part contributing to the related art may be implemented in a formof a software product. The computer software product is stored in astorage medium (for example, a ROM/RAM, a magnetic disk, or an opticaldisc), and includes several instructions for instructing a terminal(which may be a mobile phone, a computer, a server, an air conditioner,a network device, or the like) to perform the method described in theembodiments of this disclosure.

The embodiments of this disclosure are described above with reference tothe accompanying drawings, but this disclosure is not limited to theembodiments. The embodiments are only illustrative rather thanrestrictive. Inspired by this disclosure, a person of ordinary skill inthe art can still derive a plurality of variations without departingfrom the essence of this disclosure and the protection scope of theclaims. All these variations shall fall within the protection of thisdisclosure.

What is claimed is:
 1. A trigger condition configuration method, appliedto a source node or a target node and comprising: obtainingconfiguration information of a trigger condition and configurationinformation of a trigger event; and sending the configurationinformation of the trigger condition and the configuration informationof the trigger event to a terminal device, wherein an associationrelationship exists between the configuration information of the triggercondition and the configuration information of the trigger event, andconfiguration information of one trigger condition is associated withpieces of configuration information of at least two trigger events. 2.The method according to claim 1, wherein the configuration informationof the trigger condition is stored in a trigger condition informationlist, the configuration information of the trigger event is stored in atrigger event information list, and the association relationship isstored in an association relationship list; or the configurationinformation of the trigger condition and the configuration informationof the trigger event are stored in a trigger condition configurationinformation list, wherein each entry in the trigger conditionconfiguration information list comprises configuration information of atrigger condition and configuration information of at least two triggerevents corresponding to the configuration information of the triggercondition.
 3. The method according to claim 2, wherein each entry in thetrigger condition information list comprises configuration informationof a trigger condition and identification information corresponding tothe configuration information of the trigger condition; each entry inthe trigger event information list comprises configuration informationof a trigger event and identification information corresponding to theconfiguration information of the trigger event; and the associationrelationship comprises: an association relationship betweenidentification information corresponding to configuration information ofa trigger condition and an entry tag of the trigger event informationlist; or an association relationship between an entry tag of the triggercondition information list and identification information correspondingto configuration information of a trigger event; or an associationrelationship between an entry tag of the trigger condition informationlist and an entry tag of the trigger event information list; or anassociation relationship between identification informationcorresponding to configuration information of a trigger condition andidentification information in the trigger event information list; or anassociation relationship between an entry tag of the trigger conditioninformation list and identification information in the trigger eventinformation list.
 4. The method according to claim 3, wherein theassociation relationship between the identification informationcorresponding to the configuration information of the trigger conditionand the identification information in the trigger event information listcomprises: an association relationship between the identificationinformation corresponding to the configuration information of thetrigger condition and identification information corresponding toconfiguration information of a trigger event; wherein the identificationinformation corresponding to the configuration information of thetrigger event comprises at least one of: measurement identification(MeasID), target terminal identification, or event identification. 5.The method according to claim 1, wherein the configuration informationof the trigger event comprises at least one of the following: a type ofthe trigger event, a measurement parameter of the trigger event, athreshold of the trigger event, a trigger type, or trigger duration. 6.The method according to claim 5, wherein the type of the trigger eventcomprises at least one of the following: a first trigger event based ona measurement result of a target cell; a second trigger event based on ameasurement result of a serving cell; a third trigger event based on ameasurement result of a target cell and a measurement result of aserving cell; a fourth trigger event based on a packet loss rate in datatransmission of a serving cell; or a fifth trigger event based on alatency in data transmission of a serving cell.
 7. The method accordingto claim 1, wherein the configuration information of the triggercondition comprises effective duration of the trigger condition.
 8. Themethod according to claim 1, wherein when the method is applied to thesource node, the sending the configuration information of the triggercondition and the configuration information of the trigger event to theterminal device comprises: sending the configuration information of thetrigger condition and the configuration information of the trigger eventto the terminal device, after associating the configuration informationof the trigger condition with the configuration information of thetrigger event in a case that configuration information of a target cellof one or more target nodes is received.
 9. The method according toclaim 1, wherein when the method is applied to the source node, thesending the configuration information of the trigger condition and theconfiguration information of the trigger event to the terminal devicecomprises: when receiving configuration information of a target cellthat is sent by the target node, sending the configuration informationof the trigger condition and the configuration information of thetrigger event to the terminal device; or when receiving theconfiguration information of the trigger condition and the configurationinformation of the trigger event that are sent by the target node,sending the configuration information of the trigger condition and theconfiguration information of the trigger event to the terminal device;or, wherein when the method is applied to the target node, the sendingthe configuration information of the trigger condition and theconfiguration information of the trigger event to the terminal devicecomprises: when receiving request information that is sent by the sourcenode for condition-triggered cell management, sending the configurationinformation of the trigger condition and the configuration informationof the trigger event to the terminal device through the source node. 10.The method according to claim 1, wherein the pieces of configurationinformation of the at least two trigger events comprise a same firstparameter, the first parameter being a type of trigger event, the piecesof configuration information of the at least two trigger events comprisedifferent second parameters, the second parameter being at least one ofthe following: a measurement parameter of trigger event, a threshold oftrigger event, a trigger type, or trigger duration; or, wherein theconfiguration information of the trigger condition comprises effectiveduration of the trigger condition, and the effective duration of thetrigger condition is used to indicate that the trigger condition iseffective in the effective duration and is not effective beyond theeffective duration.
 11. The method according to claim 1, wherein theconfiguration information of the trigger condition and the configurationinformation of the trigger event are determined through negotiationbetween the target node and the source node.
 12. The method according toclaim 8, wherein the source node and the target node are a source basestation and a target base station respectively in a cell handoverprocedure; or, the source node and the target node are a sourcesecondary node and a target secondary node respectively in a dualconnectivity architecture.
 13. The method according to claim 9, whereinthe cell management comprises: cell handover in conditional handover;or, secondary node addition, change, release, or modification triggeredby a master node in a dual connectivity architecture; or, secondary nodeaddition, change, release, or modification triggered by a secondary nodein a dual connectivity architecture.
 14. A network-side device,comprising a processor, a memory, and a computer program stored in thememory and capable of running on the processor, wherein when the programis executed by the processor, the following steps are implemented:obtaining configuration information of a trigger condition andconfiguration information of a trigger event; and sending theconfiguration information of the trigger condition and the configurationinformation of the trigger event to a terminal device, wherein anassociation relationship exists between the configuration information ofthe trigger condition and the configuration information of the triggerevent, and configuration information of one trigger condition isassociated with pieces of configuration information of at least twotrigger events.
 15. The network-side device according to claim 14,wherein the configuration information of the trigger condition is storedin a trigger condition information list, the configuration informationof the trigger event is stored in a trigger event information list, andthe association relationship is stored in an association relationshiplist; or the configuration information of the trigger condition and theconfiguration information of the trigger event are stored in a triggercondition configuration information list, wherein each entry in thetrigger condition configuration information list comprises configurationinformation of a trigger condition and configuration information of atleast two trigger events corresponding to the configuration informationof the trigger condition.
 16. The network-side device according to claim15, wherein each entry in the trigger condition information listcomprises configuration information of a trigger condition andidentification information corresponding to the configurationinformation of the trigger condition; each entry in the trigger eventinformation list comprises configuration information of a trigger eventand identification information corresponding to the configurationinformation of the trigger event; and the association relationshipcomprises: an association relationship between identificationinformation corresponding to configuration information of a triggercondition and an entry tag of the trigger event information list; or anassociation relationship between an entry tag of the trigger conditioninformation list and identification information corresponding toconfiguration information of a trigger event; or an associationrelationship between an entry tag of the trigger condition informationlist and an entry tag of the trigger event information list; or anassociation relationship between identification informationcorresponding to configuration information of a trigger condition andidentification information in the trigger event information list; or anassociation relationship between an entry tag of the trigger conditioninformation list and identification information in the trigger eventinformation list.
 17. The network-side device according to claim 16,wherein the association relationship between the identificationinformation corresponding to the configuration information of thetrigger condition and the identification information in the triggerevent information list comprises: an association relationship betweenthe identification information corresponding to the configurationinformation of the trigger condition and identification informationcorresponding to configuration information of a trigger event; whereinthe identification information corresponding to the configurationinformation of the trigger event comprises at least one of: measurementidentification (MeasID), target terminal identification, or eventidentification.
 18. The network-side device according to claim 14,wherein the configuration information of the trigger event comprises atleast one of the following: a type of the trigger event, a measurementparameter of the trigger event, a threshold of the trigger event, atrigger type, or trigger duration; or, wherein the configurationinformation of the trigger condition comprises effective duration of thetrigger condition.
 19. The network-side device according to claim 14,wherein when the network-side device is a source node, the sending theconfiguration information of the trigger condition and the configurationinformation of the trigger event to the terminal device comprises:sending the configuration information of the trigger condition and theconfiguration information of the trigger event to the terminal device,after associating the configuration information of the trigger conditionwith the configuration information of the trigger event in a case thatconfiguration information of a target cell of one or more target nodesis received; or, wherein when the network-side device is a source node,the sending the configuration information of the trigger condition andthe configuration information of the trigger event to the terminaldevice comprises: when receiving configuration information of a targetcell that is sent by the target node, sending the configurationinformation of the trigger condition and the configuration informationof the trigger event to the terminal device; or when receiving theconfiguration information of the trigger condition and the configurationinformation of the trigger event that are sent by the target node,sending the configuration information of the trigger condition and theconfiguration information of the trigger event to the terminal device;or, wherein when the network-side device is a target node, the sendingthe configuration information of the trigger condition and theconfiguration information of the trigger event to the terminal devicecomprises: when receiving request information that is sent by the sourcenode for condition-triggered cell management, sending the configurationinformation of the trigger condition and the configuration informationof the trigger event to the terminal device through the source node. 20.The network-side device according to claim 19, wherein the source nodeand the target node are a source base station and a target base stationrespectively in a cell handover procedure; or, the source node and thetarget node are a source secondary node and a target secondary noderespectively in a dual connectivity architecture.